home *** CD-ROM | disk | FTP | other *** search
- # RadiSys EPConnect device definition file.
- #
- # $Revision: 1.8 $
- # $Date: 20 Jan 1995 14:45:16 $
- #
- # Configuration data begins at line containing ">>> Configuration starts here"
- #
- # This file defines the names for the devices reachable with EPConnect
- # software for use by the RadiSys SURM and certain other utilities,
- # possibly including the VXI configurator. This is a human editable file,
- # but beware that some utilities that edit this file may not preserve the
- # whitespace within device definitions they change.
- #
- # Device definitions have the following form:
- #
- # <definition> : <name-assignment> [,<variable-assignment>]* <newline>
- # <name-assignment> : "name" "=" <devicename>
- # <variable-assignment> : <variable>=<value>
- # <variable> : <string>
- # <value> : <string>
- #
- # A string is a sequence containing any characters except an unquoted
- # comma or equal sign. Unquoted leading or trailing whitespace characters
- # will be removed from strings.
- #
- # A devicename is an IEEE 488.2 device name.
- #
- # The variables allowed depend on the device type. In general, incorrectly
- # named variables are ignored. The form of the value assigned depends on
- # the variable. See below for expected variables and allowed values. In
- # general variable name matching is case insensitive. If the value is an
- # ordinal type (i.e. {"VME","VXI","GPIB"}) value matching is also case
- # insensitive.
- #
- # The primary application of this file if for device configuration via
- # the Start Up Resource Manager (SURM). The variables used by the SURM
- # are:
- #
- # name
- #
- # All devices must have a name variable defined. The name must conform to
- # the IEEE 488.2 spec for device names.
- #
- # media
- #
- # All devices must have a media variable defined. Valid values are VXI,
- # VME, and GPIB. The value of this variable affects the interpretation
- # of some of the other variables, and determines how the device will be
- # treated by the SURM.
- #
- # make
- # model
- #
- # All devices may have make and model variables assigned. They are used
- # for name binding in the SURM and future reference by user applications.
- # To be effective for naming VXI devices, they must match exactly one of
- # the make or model names defined in vximanuf or vximodel, respectively.
- #
- # slot
- # bus
- #
- # A VXI device may have a slot and/or bus variable defined for name binding
- # purposes. These are both in decimal. See the SURM documentation for
- # details on VXI and MXI bus numbering.
- #
- # device
- #
- # A VXI device may have a device variable defined for name binding.
- # Though rare (possibly nonexistent), it is possible for multiple devices
- # to exist within a single VXI plug-in module. This variable provides a
- # mechanism to distinguish them for naming. This value is in decimal.
- # The first device in a module is number 0.
- #
- # ula
- #
- # A VXI device may have a ula variable defined for name binding. The ULA
- # is in decimal. This is not the recommended way to name dynamically
- # configured devices, since their ULAs are not entirely predictable. For
- # historical reasons, all devices are given ULAs regardless of whether
- # they have configuration registers in A16 (or contact the VXI bus at
- # all). For non-VXI devices, the ULA is assigned based on this variable
- # if defined. Otherwise a convenient value is selected by the SURM.
- #
- # commander
- #
- # Any device may have a comander variable defined. The value of this
- # variable is the name of anotehr device. If the device and its commander
- # are both VXI, appropriate action is taken by the SURM to make the deice
- # a VXI servant of the named commander. For other media types, the
- # relationship is stored for reference.
- #
- # handlermap
- # interruptermap
- #
- # Any VXI or VME device may have interrupt maps defined by these
- # variables. The handlermap variable indicates which IRQ lines a device
- # can/will handle interrupts on. If the device is VXI, and has
- # programmable handler capability, it will be programmed to handle the
- # interrupts specified here. The interruptermap is treated
- # correspondingly. In any case, IRQ lines specified this way will not be
- # assigned by the SURM to any other PH capable VXI device. Maps for VXI
- # devices which are not found in the system are ignored (no IRQs
- # reserved). VME devices are always assumed to be present.
- # The value of these variables is a string of 7 digits. The rightmost
- # digit corresponds to interrupter or handler number 1. The digits are 1
- # through 7, and indicate the IRQ line to which the interrupter or handler
- # is connected.
- #
- # a16base
- # a16size
- # a24base
- # a24size
- # a32base
- # a32size
- #
- # VME devices use these variables to define what section of the various
- # address spaces they occupy. Values are in hex. If either size or base
- # is missing, the space is assumed to be unused by the device.
- #
- # byteorder
- #
- # VME devices use this to specify what byte order should be used
- # when accessing their memory. Use I for little-endian (Intel), or M for
- # big-endian (Motorola).
- #
- # datawidth
- #
- # VME devices use this to specify the data width that should be
- # used when accessing their memory. Use D08 (8-bit), D08O (8-bit odd
- # address only), D16 (16-bit), or D32 (32-bit).
- #
- # primary
- # secondary
- #
- # GPIB devices must have a primary variable defined. Secondary defaults
- # to 0. These form the device's address on the GPIB bus.
- #
- #
- # Lines beginning with # are comments, and are ignored.
- #
- # A single character may be quoted by placing a backslash (\) in front of it.
- # An entire string may be quoted by surrounding it with double quote
- # characters (").
- #
- # A quoted newline does not mark the end of a definition, so placing a
- # backslash at the end of a line of a definition causes the next line to
- # be treated as a continuation of the definition.
- #
- # Redundant names provide an OR function of sorts for naming constraints.
- # Variables associated with naming VXI devices within a single definition
- # are implicitly ANDed. Be aware that the first assignment of a given
- # variable (the one from the earliest definition) will be the one the SURM
- # finds. For example, no matter which of these TopCmdr definitions causes
- # the name to be assigned, the SURM will consider the configured handler map
- # to be "1", not "10".
- #
- # name=TopCmdr, \
- # media= VXI, \
- # make= "RadiSys Corp", \
- # model= EPC-7 S0, \
- # handlermap= 1, \
- #
- #
- # Here's a sample VXI device definition. This much specification is
- # sufficient if only one of this type of VXI device will be present
- # in the system.
- #
- # name=tekdmm, \
- # media= VXI, \
- # make= Tektronix, \
- # model= VX4236
- #
- #
- # Here's a sample GPIB device definition.
- #
- # name=tekps, \
- # media=GPIB, make=Tektronix, model=PS5004, \
- # primary=1
- #
- # Here's a minimal VME device definition for a device occupying 64k in A24.
- #
- # name=ram_card,\
- # media=VME, a24base=800000, a24size=10000
- #
- #
- # ----------------------------------------------------------------------------
- # ----------------------------------------------------------------------------
- # >>> Configuration starts here
-
- # This name will match any RadiSys computer with ULA==0. The resource
- # manager always has ULA==0.
- #
- # SICL normally requires that the resource manager handle all interrupts.
- #
- name=TopCmdr, \
- media= VXI, \
- ula= 0, \
- handlermap= 7654321
-